From Murillo Fernandes Bernardes <mfb@br.ibm.com>:
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Mon, 31 Oct 2005 16:10:57 +0000 (17:10 +0100)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Mon, 31 Oct 2005 16:10:57 +0000 (17:10 +0100)
commitcb3d870a1a0e686e6f8b972cd7aba1b48d31a02f
treec773b336a9f1f4f36d107f265d10aae3880dd323
parent55c3f7f34f4da112a96260b7653ea955449331b8
From Murillo Fernandes Bernardes <mfb@br.ibm.com>:

The problem is: There is no mechanism to detect block device setup failure

Network devices have the same problem, and are fixed with this too.

I handling this problem in the way suggested by aliguori:
- hotplug scripts write a "hotplug-status" node on store
- Xend DevController.createDevice() check verify this node and return success
or throw an exception on failure.
- If no changes in "hotplug-status" node after DEVICE_CREATE_TIMEOUT seconds
Xend throw an exception showing the problem with hotplug scripts.

Signed-off-by: Ewan Mellor <ewan@xensource.com>
tools/examples/block-common.sh
tools/examples/vif-bridge
tools/examples/vif-nat
tools/examples/vif-route
tools/examples/xen-hotplug-common.sh
tools/python/xen/xend/server/DevController.py